fix(ux): propagate swallowed errors in workspace resolution#131
Conversation
resolveWorkspace was discarding findWorkspace errors with _, causing misleading "doesn't exist" messages when the real error was a network failure or permission denied. Also promotes workdir resolution error logging from Debug to Warn for user visibility.
Two additional log.Debugf calls in pkg/loftconfig/config.go used %w, which produces garbled output in log functions.
✅ Deploy Preview for devsydev canceled.
|
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 38 minutes and 2 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
Summary
resolveWorkspacewas discardingfindWorkspaceerrors with_, causing misleading "workspace doesn't exist" messages when the real error was a network failure, permission denied, etc. Now propagates the actual error.resolveMergedWorkspaceFolderfromDebugtoWarnso users have visibility when workspace result loading fails.findLocalWorkspaceerror swallowing was already addressed by PR fix(workspace): propagate findWorkspace errors and fix list append bug #124 (which fixed the parentfindWorkspacefunction to propagateList()errors).